Method for obtaining internet protocol header replacement mapping and network node

ABSTRACT

The present invention discloses a method for obtaining an Internet protocol header replacement mapping, which belong to the field of communications technologies. The method includes: obtaining, by a network node, fixed IP header information which is bound to a UE, where the network node is an MME or an eNB or a PGW or an SGW; establishing an IP header replacement mapping according to the fixed IP header information, where the IP header replacement mapping is correspondence between the fixed IP header information and an index or a bearer; and performing data transmission with the UE according to the IP header replacement mapping. In the present invention, the network node establishes the IP header replacement mapping according to the obtained fixed IP header information which is bound to the UE, the method is more flexible.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2012/086493, filed on Dec. 13, 2012, which claims priority toChinese Patent Application No. 201110430097.6, filed on Dec. 20, 2011,both of which are hereby incorporated by reference in their entireties.

TECHNICAL FIELD

The present invention relates to the field of communicationstechnologies, and in particular, to a method for obtaining an Internetprotocol header replacement mapping and a network node.

BACKGROUND

With wide applications of the Internet of Things, the number of usersaccessing the network continuously grows. During data transmissionbetween objects based on IP (Internet Protocol, Internet protocol),overheads produced an IP header in the communication data are huge,resulting in extremely low user plane transmission efficiency.Therefore, by establishing a replacement mapping between the IP headerand an index and replacing the IP header with a corresponding index,applications of performing data transmission according to the index ofthe IP header emerge as required.

In the prior art, an IP header replacement mapping is configured by anMTC (Machine Type Communication, machine type communication) server ormanually configured to an eNB (evolved Node B, evolved base station),and the eNB maintains the IP header replacement mapping and performsdata transmission with a UE (User Equipment, user equipment) accordingto the IP header replacement mapping.

In the implementation of the present invention, the inventor finds thatthe prior art at least has the following problems:

In the prior art, because the IP header replacement mapping obtained bythe eNB is configured by the MTC server or manually configured, thismanner for obtaining an IP header replacement mapping is inflexible andnot easy to update or maintain; moreover, in a current network, nodirect interface exists between the eNB and the MTC server, so that itis rather difficult to configure and maintain the mapping table.

SUMMARY

To improve the flexibility in obtaining the IP header replacementmapping and reducing the difficulty in configuring and maintaining theIP header replacement mapping, embodiments of the present inventionprovide a method for obtaining an Internet protocol header replacementmapping and a network node. The technical solutions are as follows:

In one aspect, a method for obtaining an Internet protocol headerreplacement mapping is provided, which includes:

obtaining, by a network node, fixed Internet protocol IP headerinformation which is bound to a user equipment UE, where the networknode is a mobility management entity MME or an evolved base station eNBor a packet data network gateway PGW or a serving gateway SGW;

establishing an IP header replacement mapping according to the fixed IPheader information, where the IP header replacement mapping iscorrespondence between the fixed IP header information and an index or abearer; and

performing data transmission with the UE according to the IP headerreplacement mapping.

In another aspect, a network node is further provided, where the networknode is a mobility management entity MME or an evolved base station eNBor a packet data network gateway PGW or a serving gateway SGW, andincludes:

an obtaining module, configured to obtain fixed Internet protocol IPheader information which is bound to a user equipment UE;

an establishing module, configured to establish an IP header replacementmapping according to the fixed IP header information obtained by theobtaining module, where the IP header replacement mapping iscorrespondence between the fixed IP header information and an index or abearer; and

a communication module, configured to perform data transmission with theUE according to the IP header replacement mapping established by theestablishing module.

The technical solutions provided by the embodiments of the presentinvention have the following beneficial effects:

The network node establishes the IP header replacement mapping accordingto the obtained fixed IP header information which is bound to the UE,which, compared with an existing manner of configuring the mapping by anMTC server or manually, is more flexible and can reduce difficulty inconfiguring and maintaining the IP header replacement mapping; moreover,by expanding an entity for maintaining the IP header replacement mappingfrom an eNB in the prior art to a network node such as an eNB, or anMME, or a PGW, or an SGW, flexibility in obtaining the IP headerreplacement mapping is further improved and the implementation mannerbecomes more universal.

BRIEF DESCRIPTION OF DRAWINGS

To illustrate the technical solutions according to the embodiments ofthe present invention more clearly, the accompanying drawings fordescribing the embodiments are introduced briefly in the following.Apparently, the accompanying drawings in the following description areonly some embodiments of the present invention, and persons of ordinaryskill in the art can derive other drawings from the accompanyingdrawings without creative efforts.

FIG. 1 is a schematic structural diagram of a protocol layer of anetwork node according to Embodiment 1 of the present invention;

FIG. 2 is a flow chart of a method for obtaining an Internet protocolheader replacement mapping according to Embodiment 1 of the presentinvention;

FIG. 3 is a flow chart of a method for obtaining an Internet protocolheader replacement mapping according to Embodiment 2 of the presentinvention;

FIG. 4 is a schematic diagram of interaction between network nodesaccording to Embodiment 2 of the present invention;

FIG. 5 is another schematic diagram of interaction between network nodesaccording to Embodiment 2 of the present invention;

FIG. 6 is a flow chart of a method for obtaining an Internet protocolheader replacement mapping according to Embodiment 3 of the presentinvention;

FIG. 7 is a flow chart of a method for obtaining an Internet protocolheader replacement mapping according to Embodiment 4 of the presentinvention;

FIG. 8 is a flow chart of a method for obtaining an Internet protocolheader replacement mapping according to Embodiment 5 of the presentinvention;

FIG. 9 is a schematic structural diagram of a network node according toEmbodiment 6 of the present invention;

FIG. 10 is a schematic structural diagram of a communication moduleaccording to Embodiment 6 of the present invention;

FIG. 11 is a schematic structural diagram of another communicationmodule according to Embodiment 6 of the present invention;

FIG. 12 is a schematic structural diagram of another communicationmodule according to Embodiment 6 of the present invention;

FIG. 13 is a schematic structural diagram of another communicationmodule according to Embodiment 6 of the present invention; and

FIG. 14 is a schematic structural diagram of another communicationmodule according to Embodiment 6 of the present invention.

DESCRIPTION OF EMBODIMENTS

In order to make the objectives, technical solutions, and advantages ofthe present invention more comprehensible, embodiments of the presentinvention are described in further detail below with reference to theaccompanying drawings.

Embodiment 1

This embodiment provides a method for obtaining an Internet protocolheader replacement mapping. FIG. 1 is a schematic structural diagram ofa protocol layer of a network node. In the method provided by thisembodiment, a network node for obtaining an IP header replacementmapping is expanded from a single eNB to an eNB or an MME (MobilityManagement Entity, mobility management entity) or a PGW (Packet DataNetwork Gateway, packet data network gateway) or an SGW (ServingGateway, serving gateway), so as to improve flexibility in obtaining theIP header replacement mapping. As shown in FIG. 1, when IP packet headerrecovery needs to be executed in the PGW, an IP compression layer may beprovided on a PDCP (Packet Data Convergence Protocol, packet dataconvergence protocol) layer of a UE, and a peer end of the layer is inthe PGW and executes IP header replacement/compression and recoveryfunctions. Similarly, an IP compression layer of the peer end may alsobe located on the PDCP layer of the eNB, so that the IP headerreplacement/compression process is completed between the UE and the eNB.The IP compression layer of the peer end may also be located in the MME,and when a CP is used for data transmission between the UE and the MME,the IP header replacement/compression process is completed between theUE and the MME. In combination with the structure of the protocol layerof the network node shown in FIG. 1, referring to FIG. 2, a procedure ofthe method provided by this embodiment is specifically as follows:

201: A network node obtains fixed IP header information which is boundto a UE, where the network node is an MME or an eNB or a PGW or an SGW.

202: Establish an IP header replacement mapping according to the fixedIP header information, where the IP header replacement mapping iscorrespondence between the fixed IP header information and an index or abearer.

203: Perform data transmission with the UE according to the IP headerreplacement mapping.

When the network node is an MME or an eNB, the obtaining the fixed IPheader information which is bound to the UE includes:

obtaining, from the UE or an HSS (Home Subscriber Server, homesubscriber server), the fixed IP header information which is bound tothe UE.

Alternatively, when the network node is a PGW or an SGW or an eNB, theobtaining the fixed IP header information which is bound to the UEincludes:

receiving the fixed IP header information sent by an MME after the MMEobtains, from the UE or an HSS, the fixed IP header information which isbound to the UE.

Further, the obtaining, from the UE, the fixed IP header informationwhich is bound to the UE includes:

when the UE initiates an attach request or a dedicated bearer setupprocess, obtaining, from the UE, the fixed IP header information whichis bound to the UE.

Further, the obtaining, from the UE, the fixed IP header informationwhich is bound to the UE includes:

receiving fixed IP header information which is bound to the UE andactively reported by the UE, or after querying the UE, receiving fixedIP header information which is bound to the UE and reported by the UE.

Specifically, when the network node is an MME, the performing datatransmission with the UE according to the IP header replacement mappingincludes:

sending the IP header replacement mapping to another network node, sothat the another network node performs data transmission with the UEaccording to the IP header replacement mapping.

Optionally, when the IP header replacement mapping is correspondencebetween the fixed IP header information and an index, the performingdata transmission with the UE according to the IP header replacementmapping includes:

sending the IP header replacement mapping to the UE, and receiving adata packet sent by the UE after the UE replaces the corresponding fixedIP header information with the index in the IP header replacementmapping; and

querying the IP header replacement mapping according to the index in thedata packet sent by the UE, to obtain the fixed IP header informationcorresponding to the data packet sent by the UE.

Further, after the obtaining the fixed IP header informationcorresponding to the data packet sent by the UE, the method furtherincludes:

recovering the index in the data packet sent by the UE to thecorresponding fixed IP header information, and forwarding the fixed IPheader information to another network node.

Optionally, when the IP header replacement mapping is correspondencebetween the fixed IP header information and an index, the performingdata transmission with the UE according to the IP header replacementmapping includes:

sending the IP header replacement mapping to the UE, and sending, to theUE, a data packet where the corresponding fixed IP header information isreplaced with the index in the IP header replacement mapping, so thatthe UE queries the IP header replacement mapping according to the indexin the received data packet, to obtain the fixed IP header informationcorresponding to the received data packet.

Optionally, when the IP header replacement mapping is correspondencebetween the fixed IP header information and a bearer, the performingdata transmission with the UE according to the IP header replacementmapping includes:

indicating, according to the IP header replacement mapping, a bearer forthe UE to send data, and receiving a data packet which is sent by the UEon the indicated bearer and has no fixed IP header information added;and

querying the IP header replacement mapping according to the bearer forthe UE to send the data packet, to obtain the fixed IP headerinformation corresponding to the data packet sent by the UE.

Further, after the obtaining the fixed IP header informationcorresponding to the data packet sent by the UE, the method furtherincludes:

adding the corresponding fixed IP header information in the data packetsent by the UE, and forwarding the data packet to another network node.

In the method provided by this embodiment, the network node establishesthe IP header replacement mapping according to the obtained fixed IPheader information which is bound to the UE, so, compared with anexisting manner of configuring the mapping by an MTC server or manually,the method is more flexible and can reduce difficulty in configuring andmaintaining the IP header replacement mapping; moreover, by expanding anentity for maintaining the IP header replacement mapping from an eNB inthe prior art to a network node such as an eNB, or an MME, or a PGW, oran SGW, flexibility in obtaining the IP header replacement mapping isfurther improved and the implementation manner becomes more universal.

Regarding different network nodes and technical means for obtaining anIP header replacement mapping, to more clearly illustrate the methodprovided by Embodiment 1, the content in Embodiment 2 to Embodiment 5 istaken as examples to describe in detail the method provided inEmbodiment 1. The details are shown in Embodiment 2 to Embodiment 5 asfollows:

Embodiment 2

This embodiment provides a method for obtaining an Internet protocolheader replacement mapping, and based on Embodiment 1, for ease ofillustration, it is taken as an example in this embodiment that a PGWreceives fixed IP header information sent by an MME and establishes anIP header replacement mapping, where the established IP headerreplacement mapping is correspondence between the fixed IP headerinformation and an index, so as to illustrate in detail the methodprovided by this embodiment. Referring to FIG. 3, a procedure of themethod provided by this embodiment is specifically as follows:

301: A PGW receives fixed IP header information sent by an MME after theMME obtains, from a UE or an HSS, the fixed IP header information whichis bound to the UE.

In this step, specific content of the fixed IP header information whichis bound to the UE and obtained by the MME from the UE or HSS is notlimited in this embodiment, and in an actual application, the fixed IPheader information may be a fixed part of content in an IP packet headerof an APN (Access Point Name, access point name) which is bound to theUE, where the fixed part of content includes, but not limited to,information such as a version, header length, service type, time tolive, source IP address and destination IP address.

Further, when obtaining, from the UE, the fixed IP header informationwhich is bound to the UE, the MME may receive the fixed IP headerinformation which is bound to the UE and actively reported by the UE, orafter querying the UE, receive the fixed IP header information which isbound to the UE and reported by the UE. This embodiment is notspecifically limited thereto.

302: The PGW establishes an IP header replacement mapping according tothe obtained fixed IP header information, where the IP headerreplacement mapping is correspondence between the fixed IP headerinformation and an index.

Specifically, the IP header replacement mapping established by the PGWaccording to the obtained fixed IP header information is correspondencebetween the fixed IP header information and an index. The IP headerreplacement mapping is established so that an index of a small overheadcan be used to replace the fixed IP header information of a largeoverhead for data transmission in a subsequent communication process,thereby reducing the overhead and improving user plane data transmissionefficiency. Therefore, this embodiment does not limit the specific indexcorresponding to the fixed IP header information, as long as theoverhead of the the index that is induced is ensured to be smaller thanthat of the fixed IP header information. In an actual application, fordifferent bearers, fixed IP information may be different. In this case,if the PGW obtains different fixed IP information, different IP headerreplacement mappings may be established according to the obtained fixedIP header information, and to facilitate subsequent communication withcorresponding UEs according to the different IP header replacementmappings, the PGW may store the established IP header replacementmapping in the form of a list, or store the established IP headerreplacement mapping in other forms. This embodiment does not limit themanner of establishing and storing the IP header replacement mapping bythe PGW.

303: The PGW sends the established IP header replacement mapping to theUE, and receives a data packet sent by the UE after the UE replaces thecorresponding fixed IP header information with the index in the IPheader replacement mapping.

In this step, after the PGW sends the established IP header replacementmapping to the UE, for different bearers, fixed IP information may bedifferent, and therefore, IP header replacement mappings sent by the PGWand received by the UE may also be different. In this case, tofacilitate subsequent communication with corresponding network nodesaccording to the different IP header replacement mappings, the UE maystore the received IP header replacement mapping in the form of a list,or store the received IP header replacement mapping in other forms. Thisembodiment does not limit the manner of storing the IP headerreplacement mapping by the UE.

After the UE receives the IP header replacement mapping sent by the PGW,the UE may obtain an index corresponding to the fixed IP headerinformation according to the IP header replacement mapping, and replacethe fixed IP header information of a large overhead with an index of asmall overhead for data transmission, thereby reducing the overhead andimproving the user plane data transmission efficiency. In addition, themethod provided by this embodiment also supports a data compressionmanner, and this embodiment does not limit the specific compressionmanner adopted herein, for example, after substituting the correspondingfixed IP header information with the index in the IP header replacementmapping, the UE adopts a PDCP compression technology to compress a datapacket to be sent, and sends the compressed data packet to the PGW,thereby further reducing the overhead and improving the user plane datatransmission efficiency.

304: The PGW queries the IP header replacement mapping according to theindex in the data packet sent by the UE, to obtain the fixed IP headerinformation corresponding to the data packet sent by the UE.

Because the index in the data packet sent by the UE is obtained based onthe IP header replacement mapping established by the PGW, afterreceiving the data packet sent by the UE, the PGW may query the IPheader replacement mapping according to the index in the data packetsent by the UE, to obtain the fixed IP header information correspondingto the data packet sent by the UE. If the UE compresses the data packetin step 303, the PGW further needs to decompress the received datapacket. This embodiment does not limit the specific decompressionmanner.

305: The PGW recovers the index in the data packet sent by the UE to thecorresponding fixed IP header information, and forwards the fixed IPheader information to another network node.

In this step, when sending the data packet, the UE replaces thecorresponding fixed IP header information with the index in the IPheader replacement mapping, and only the PGW and the UE side have the IPheader replacement mapping. Therefore, to enable another network node tolearn the fixed IP header information corresponding to the data packetsent by the UE, before forwarding the data packet sent by the UE to theanother network node, the PGW needs to recover the index in the datapacket sent by the UE to the corresponding fixed IP header information,and then forward the fixed IP header information to the another networknode. This embodiment does not specifically limit the another networknode.

Moreover, in the method provided by this embodiment, after sending theestablished IP header replacement mapping to the UE, the PGW can notonly implement uplink data transmission by performing step 303 to step305, but also can perform downlink data transmission. For example, thePGW sends the established IP header replacement mapping to the UE, andsends, to the UE, a data packet where the corresponding fixed IP headerinformation is replaced with the index in the IP header replacementmapping, so that the UE queries the IP header replacement mappingaccording to the index in the received data packet, to obtain the fixedIP header information corresponding to the received data packet. In thedata transmission manner, the PGW may perform data compression, and theUE performs data decompression.

It should be noted that, the foregoing method may be implemented basedon a UE attach process, that is, when obtaining the fixed IP headerinformation which is bound to the UE, the MME may obtain, from the UE,the fixed IP header information which is bound to the UE, when the UEinitiates an attach request; for this scenario, an interaction processbetween the network nodes may be shown in FIG. 4. Optionally, inaddition to the UE attach process, the foregoing method may also beimplemented based on another process, for example, based on a dedicatedbearer setup process, so that when obtaining the fixed IP headerinformation which is bound to the UE, the MME may obtain, from the UEand in the dedicated bearer process, the fixed IP header informationwhich is bound to the UE; for this scenario, an interaction processbetween the network nodes may be shown in FIG. 5.

Further, in addition to the PGW, the network node which establishes theIP header replacement mapping according to the fixed IP headerinformation which is bound to the UE and sent by the MME, and performsdata transmission with the UE according to the established IP headerreplacement mapping may also be an eNB or an SGW, the implementationprocess of which is similar to the method provided by this embodiment,so the details are not repeated herein.

In the method provided by this embodiment, the network node establishesthe IP header replacement mapping according to the obtained fixed IPheader information which is bound to the UE, so, compared with anexisting manner of configuring the mapping by an MTC server or manually,the method is more flexible and can reduce difficulty in configuring andmaintaining the IP header replacement mapping; moreover, by expanding anentity for maintaining the IP header replacement mapping from an eNB inthe prior art to a network node such as a PGW or an eNB or an SGW,flexibility in obtaining the IP header replacement mapping is furtherimproved and the implementation manner becomes more universal.

Embodiment 3

This embodiment provides a method for obtaining an Internet protocolheader replacement mapping, and based on Embodiment 1, for ease ofillustration, it is taken as an example in this embodiment that a PGWreceives fixed IP header information sent by an MME and establishes anIP header replacement mapping, where the established IP headerreplacement mapping is correspondence between the fixed IP headerinformation and a bearer, so as to illustrate in detail the methodprovided by this embodiment. Referring to FIG. 6, a procedure of themethod provided by this embodiment is specifically as follows:

601: A PGW receives fixed IP header information sent by an MME after theMME obtains, from a UE or an HSS, the fixed IP header information whichis bound to the UE.

In this step, for the specific content of the fixed IP headerinformation which is bound to the UE and obtained by the MME from the UEor HSS and the specific obtaining manner thereof, reference may be madeto step 301 in Embodiment 2, and the details are not repeated herein.

602: The PGW establishes an IP header replacement mapping according tothe obtained fixed IP header information, where the IP headerreplacement mapping is correspondence between the fixed IP headerinformation and a bearer.

Specifically, the IP header replacement mapping established by the PGWaccording to the obtained fixed IP header information is thecorrespondence between the fixed IP header information and the bearer.The IP header replacement mapping is established to enable the UE tosend a data packet, containing no fixed IP header information, on anindicated bearer in the subsequent communication process, therebyreducing the overhead and improving the user plane data transmissionefficiency. Therefore, this embodiment does not limit the specificbearer corresponding to the fixed IP header information. In an actualapplication, for different bearers, fixed IP information may bedifferent. In this case, if the PGW obtains different fixed IPinformation, different IP header replacement mappings may be establishedaccording to the obtained fixed IP header information, and to facilitatesubsequent communication with corresponding UEs according to thedifferent IP header replacement mappings, the PGW may store theestablished IP header replacement mapping in the form of a list, orstore the established IP header replacement mapping in other forms. Thisembodiment does not limit the manner of establishing and storing the IPheader replacement mapping by the PGW.

603: The PGW indicates, according to the IP header replacement mapping,a bearer for the UE to send data, and receives a data packet which issent by the UE on the indicated bearer and has no fixed IP headerinformation added.

In this step, after establishing the IP header replacement mapping, thePGW does not adopt a manner of feeding back the established IP headerreplacement mapping to the UE, but only indicates a bearer for the UE tosend data, so that the UE sends, on the indicated bearer, a data packetthat has no fixed IP header information added, which also achieves thepurpose of saving the overhead and increasing a transmission rate. Inaddition, the method provided by this embodiment also supports a datacompression manner, and this embodiment does not limit the specificcompression manner adopted herein, for example, the UE adopts a PDCPcompression technology to compress a data packet to be sent, and sends,on the indicated bearer, the compressed data packet to the PGW, therebyfurther reducing the overhead and improving the user plane datatransmission efficiency.

604: The PGW queries the IP header replacement mapping according to thebearer for the UE to send the data packet, to obtain the fixed IP headerinformation corresponding to the data packet sent by the UE.

Specifically, because the data packet sent by the UE is sent on thebearer indicated by the PGW, the PGW can determine the fixed IP headerinformation corresponding to the bearer when indicating the bearer tothe UE, and therefore, when the PGW receives the data packet sent by theUE on the indicated bearer, the PGW queries the IP header replacementmapping according to the bearer for the UE to send the data packet, todetermine and obtain the fixed IP header information corresponding tothe data packet sent by the UE. If the UE compresses the data packet instep 603, the PGW further needs to decompress the received data packet.This embodiment does not limit the specific decompression manner.

It should be noted that, to ensure the correspondence between the bearerindicated by the PGW to the UE and the fixed IP header information, themethod provided by this embodiment is applicable to a case that onebearer merely sends data to the same IP address.

605: The PGW adds the corresponding fixed IP header information in thedata packet sent by the UE, and forwards the data packet to anothernetwork node.

In this step, after the PGW determines the fixed IP header informationcorresponding to the data packet sent by the UE, to enable anothernetwork node to learn the fixed IP header information corresponding tothe data packet sent by the UE, before forwarding the data packet sentby the UE to the another network node, the PGW needs to add thecorresponding fixed IP header information in the data packet sent by theUE, and then forward the data packet to the another network node. Thisembodiment does not specifically limit the another network node.

It should be noted that, the foregoing method may be implemented basedon a UE attach process, that is, when obtaining the fixed IP headerinformation which is bound to the UE, the MME may obtain, from the UE,the fixed IP header information which is bound to the UE, when the UEinitiates an attach request. Optionally, in addition to the UE attachprocess, the foregoing method may also be implemented based on anotherprocess, for example, based on a dedicated bearer setup process, so thatwhen obtaining the fixed IP header information which is bound to the UE,the MME may obtain, from the UE and in the dedicated bearer process, thefixed IP header information which is bound to the UE.

Further, in addition to the PGW, the network node which establishes theIP header replacement mapping according to the fixed IP headerinformation which is bound to the UE and sent by the MME, and performsdata transmission with the UE according to the established IP headerreplacement mapping may also be an eNB or an SGW, the implementationprocess of which is similar to the method provided by this embodiment,so the details are not repeated herein.

In the method provided by this embodiment, the network node establishesthe IP header replacement mapping according to the obtained fixed IPheader information which is bound to the UE, so, compared with anexisting manner of configuring the mapping by an MTC server or manually,the method is more flexible and can reduce difficulty in configuring andmaintaining the IP header replacement mapping; moreover, by expanding anentity for maintaining the IP header replacement mapping from an eNB inthe prior art to a network node such as a PGW or an eNB or an SGW,flexibility in obtaining the IP header replacement mapping is furtherimproved and the implementation manner becomes more universal.

Embodiment 4

This embodiment provides a method for obtaining an Internet protocolheader replacement mapping, and based on Embodiment 1, for ease ofillustration, it is taken as an example in this embodiment that an MMEobtains, from a UE or an HSS, fixed IP header information which is boundto the UE and establishes an IP header replacement mapping, where theestablished IP header replacement mapping is correspondence between thefixed IP header information and an index, so as to illustrate in detailthe method provided by this embodiment. Referring to FIG. 7, a procedureof the method provided by this embodiment is specifically as follows:

701: An MME obtains, from a UE or an HSS, fixed IP header informationwhich is bound to the UE.

In this step, the manner that the MME obtains, from the UE or HSS, thefixed IP header information which is bound to the UE is the same as step301 in Embodiment 2, and the details are not repeated herein.

702: The MME establishes an IP header replacement mapping according tothe obtained fixed IP header information, where the IP headerreplacement mapping is correspondence between the fixed IP headerinformation and an index.

Specifically, the IP header replacement mapping established by the MMEaccording to the obtained fixed IP header information is thecorrespondence between the fixed IP header information and the index.The IP header replacement mapping is established so that an index ofsmall overhead can be used to replace the fixed IP header information oflarge overhead for data transmission in the subsequent communicationprocess, thereby reducing the overhead and improving the user plane datatransmission efficiency. Therefore, this embodiment does not limit thespecific index corresponding to the fixed IP header information, as longas the overhead of the the index that is induced is ensured to besmaller than that of the fixed IP header information. In an actualapplication, for different bearers, fixed IP information may bedifferent. In this case, if the MME obtains different fixed IPinformation, different IP header replacement mappings may be establishedaccording to the obtained fixed IP header information, and to facilitatesubsequent communication with corresponding UEs according to thedifferent IP header replacement mappings, the MME may store theestablished IP header replacement mapping in the form of a list, orstore the established IP header replacement mapping in other forms. Thisembodiment does not limit the manner of establishing and storing the IPheader replacement mapping by the MME.

703: The MME sends the established IP header replacement mapping to theUE, and receives a data packet sent by the UE after the UE replaces thecorresponding fixed IP header information with the index in the IPheader replacement mapping.

In this step, after the MME sends the established IP header replacementmapping to the UE, for different bearers, fixed IP information may bedifferent, and therefore, header replacement mappings sent by the MMEand received by the UE may also be different. In this case, tofacilitate subsequent communication with corresponding network nodesaccording to the different IP header replacement mappings, the UE maystore the received IP header replacement mapping in the form of a list,or store the received IP header replacement mapping in other forms. Thisembodiment does not limit the manner of storing the IP headerreplacement mapping by the UE.

After the UE receives the IP header replacement mapping sent by the MME,the UE may obtain an index corresponding to the fixed IP headerinformation according to the IP header replacement mapping, and replacethe fixed IP header information of a large overhead with an index of asmall overhead for data transmission, thereby reducing the overhead andimproving the user plane data transmission efficiency. In addition, themethod provided by this embodiment also supports a data compressionmanner, and this embodiment does not limit the specific compressionmanner adopted herein, for example, after substituting the correspondingfixed IP header information with the index in the IP header replacementmapping, the UE adopts a PDCP compression technology to compress a datapacket to be sent, and sends the compressed data packet to the MME,thereby further reducing the overhead and improving the user plane datatransmission efficiency.

704: The MME queries the IP header replacement mapping according to theindex in the data packet sent by the UE, to obtain the fixed IP headerinformation corresponding to the data packet sent by the UE.

Because the index in the data packet sent by the UE is obtained based onthe IP header replacement mapping established by the MME, afterreceiving the data packet sent by the UE, the MME may query the IPheader replacement mapping according to the index in the data packetsent by the UE, to obtain the fixed IP header information correspondingto the data packet sent by the UE. If the UE compresses the data packetin step 703, the MME further needs to decompress the received datapacket. This embodiment does not limit the specific decompressionmanner.

705: The MME recovers the index in the data packet sent by the UE to thecorresponding fixed IP header information, and forwards the fixed IPheader information to another network node.

In this step, when sending the data packet, the UE replaces thecorresponding fixed IP header information with the index in the IPheader replacement mapping, and only the MME and the UE side have the IPheader replacement mapping. Therefore, before forwarding the data packetsent by the UE, to enable another network node to learn the fixed IPheader information corresponding to the data packet sent by the UE, theMME needs to recover the index in the data packet sent by the UE to thecorresponding fixed IP header information, and then forward the fixed IPheader information to the another network node. This embodiment does notspecifically limit the another network node.

Moreover, in the method provided by this embodiment, after sending theestablished IP header replacement mapping to the UE, the MME can notonly perform step 703 to step 705 to implement uplink data transmission,but also can perform downlink data transmission. For example, the MMEsends the established IP header replacement mapping to the UE, andsends, to the UE, a data packet where the corresponding fixed IP headerinformation is replaced with the index in the IP header replacementmapping, so that the UE queries the IP header replacement mappingaccording to the index in the received data packet, to obtain the fixedIP header information corresponding to the received data packet.

It should be noted that, the foregoing method may be implemented basedon a UE attach process, that is, when obtaining the fixed IP headerinformation which is bound to the UE, the MME may obtain, from the UE,the fixed IP header information which is bound to the UE, when the UEinitiates an attach request. Optionally, in addition to the UE attachprocess, the foregoing method may also be implemented based on anotherprocess, for example, based on a dedicated bearer setup process, so thatwhen obtaining the fixed IP header information which is bound to the UE,the MME may obtain, from the UE and in the dedicated bearer process, thefixed IP header information which is bound to the UE.

Further, in addition to the MME, the network node which establishes theIP header replacement mapping and performs data transmission with the UEaccording to the established IP header replacement mapping may also bean eNB, the implementation process of which is similar to the methodprovided by this embodiment, so the details are not repeated herein. Ifthe network node that establishes the IP header replacement mapping isan eNB, when obtaining the fixed IP header information which is bound tothe UE, the eNB can multiplex an existing RRC (Radio Resource Control,radio resource control) message or a new RRC message to carry the fixedIP header information, for example, an RRC connection setup completemessage is used in the uplink, and an RRC connection reconfigurationmessage is used in the downlink.

Optionally, in the method provided by this embodiment, in addition toestablishing the IP header replacement mapping, the MME can perform datatransmission with the UE through the IP header replacement mapping andcan also send the established IP header replacement mapping to anothernetwork node, so that the another network node performs datatransmission with the UE according to the IP header replacement mappingestablished by the MME, and the MME does not need to recover the indexin the data packet sent by the UE to the corresponding fixed IP headerinformation and then forward the fixed IP header information to theanother network node. When the another network node performs datatransmission with the UE according to the IP header replacement mappingestablished by the MME, the specific implementation manner is similar tothe execution process of the MME in step 703 to step 705 of thisembodiment, and the details are not repeated herein.

In the method provided by this embodiment, the network node establishesthe IP header replacement mapping according to the obtained fixed IPheader information which is bound to the UE, so, compared with anexisting manner of configuring the mapping by an MTC server or manually,the method is more flexible and can reduce difficulty in configuring andmaintaining the IP header replacement mapping; moreover, by expanding anentity for maintaining the IP header replacement mapping from an eNB inthe prior art to a network node such as a PGW or an eNB or an SGW,flexibility in obtaining the IP header replacement mapping is furtherimproved and the implementation manner becomes more universal.

Embodiment 5

This embodiment provides a method for obtaining an Internet protocolheader replacement mapping, and based on Embodiment 1, for ease ofillustration, it is taken as an example in this embodiment that an MMEobtains fixed IP header information which is bound to a UE andestablishes an IP header replacement mapping, where the established IPheader replacement mapping is correspondence between the fixed IP headerinformation and a bearer, so as to illustrate in detail the methodprovided by this embodiment. Referring to FIG. 8, a procedure of themethod provided by this embodiment is specifically as follows:

801: An MME obtains, from a UE or an HSS, fixed IP header informationwhich is bound to the UE.

In this step, for the specific content of the fixed IP headerinformation which is bound to the UE and obtained by the MME from the UEor HSS and the specific obtaining manner thereof, reference may be madeto step 301 in Embodiment 2, and the details are not repeated herein.

802: The MME establishes an IP header replacement mapping according tothe obtained fixed IP header information, where the IP headerreplacement mapping is correspondence between the fixed IP headerinformation and a bearer.

Specifically, the IP header replacement mapping established by the MMEaccording to the obtained fixed IP header information is thecorrespondence between the fixed IP header information and the bearer.The IP header replacement mapping is established to enable the UE tosend a data packet, containing no fixed IP header information, on anindicated bearer in the subsequent communication process, therebyreducing the overhead and improving the user plane data transmissionefficiency. Therefore, this embodiment does not limit the specificbearer corresponding to the fixed IP header information. In an actualapplication, for different bearers, fixed IP information may bedifferent. In this case, if the MME obtains different fixed IPinformation, different IP header replacement mappings may be establishedaccording to the obtained fixed IP header information, and to facilitatesubsequent communication with corresponding UEs according to thedifferent IP header replacement mappings, the MME may store theestablished IP header replacement mapping in the form of a list, orstore the established IP header replacement mapping in other forms. Thisembodiment does not limit the manner of establishing and storing the IPheader replacement mapping by the MME.

803: The MME indicates, according to the fixed IP header information inthe IP header replacement mapping, a bearer for the UE to send data, andreceives a data packet which is sent by the UE on the indicated bearerand has no the fixed IP header information added.

In this step, after establishing the IP header replacement mapping, theMME does not adopt a manner of feeding back the established IP headerreplacement mapping to the UE, but only indicates a bearer for the UE tosend data, so that the UE sends, on the indicated bearer, a data packetthat has no the fixed IP header information added, which also achievesthe purpose of saving the overhead and increasing the transmission rate.In addition, the method provided by this embodiment also supports a datacompression manner, and this embodiment does not limit the specificcompression manner adopted herein, for example, the UE adopts a PDCPcompression technology to compress a data packet to be sent, and sends,on the indicated bearer, the compressed data packet to the MME, therebyfurther reducing the overhead and improving the user plane datatransmission efficiency.

804: The MME queries the IP header replacement mapping according to thebearer for the UE to send the data packet, to obtain the fixed IP headerinformation corresponding to the data packet sent by the UE.

Specifically, because the data packet sent by the UE is sent on thebearer indicated by the MME, the MME can determine the fixed IP headerinformation corresponding to the bearer when indicating the bearer tothe UE, and therefore, when the MME receives the data packet sent by theUE on the indicated bearer, the MME queries the IP header replacementmapping according to the bearer for the UE to send the data packet, todetermine and obtain the fixed IP header information corresponding tothe data packet sent by the UE. If the UE compresses the data packet instep 803, the MME further needs to decompress the received data packet.This embodiment does not limit the specific decompression manner.

It should be noted that, to ensure the correspondence between the bearerindicated by the MME to the UE and the fixed IP header information, themethod provided by this embodiment is applicable to a case that onebearer merely sends data to the same IP address.

805: The MME adds the corresponding fixed IP header information in thedata packet sent by the UE, and forwards the data packet to anothernetwork node.

In this step, after the MME determines the fixed IP header informationcorresponding to the data packet sent by the UE, to enable anothernetwork node to learn the fixed IP header information corresponding tothe data packet sent by the UE, before forwarding the data packet sentby the UE to the another network node, the MME needs to add thecorresponding fixed IP header information in the data packet sent by theUE, and then forward the data packet to the another network node. Thisembodiment does not specifically limit the another network node.

It should be noted that, the foregoing method may be implemented basedon a UE attach process, that is, when obtaining the fixed IP headerinformation which is bound to the UE, the MME may obtain, from the UE,the fixed IP header information which is bound to the UE, when the UEinitiates an attach request. Optionally, in addition to the UE attachprocess, the foregoing method may also be implemented based on anotherprocess, for example, based on a dedicated bearer setup process, so thatwhen obtaining the fixed IP header information which is bound to the UE,the MME may obtain, from the UE and in the dedicated bearer process, thefixed IP header information which is bound to the UE.

Further, in addition to the MME, the network node which establishes theIP header replacement mapping and performs data transmission with the UEaccording to the established IP header replacement mapping may also bean eNB, the implementation process of which is similar to the methodprovided by this embodiment, so the details are not repeated herein. Ifthe network node that establishes the IP header replacement mapping isan eNB, when obtaining the fixed IP header information which is bound tothe UE, the eNB can multiplex an existing RRC message or a new RRCmessage to carry the fixed IP header information, for example, an RRCconnection setup complete message is used in the uplink, and an RRCconnection reconfiguration message is used in the downlink.

Optionally, in the method provided by this embodiment, in addition toestablishing the IP header replacement mapping, the MME can perform datatransmission with the UE through the IP header replacement mapping andcan also send the established IP header replacement mapping to anothernetwork node, so that the another network node performs datatransmission with the UE according to the IP header replacement mappingestablished by the MME, and the MME does not need to recover an index inthe data packet sent by the UE to a corresponding fixed IP headerinformation and then forward the fixed IP header information to theanother network node. When the another network node performs datatransmission with the UE according to the IP header replacement mappingestablished by the MME, the specific implementation manner is similar tothe execution process of the MME in step 803 to step 805 of thisembodiment, and the details are not repeated herein.

In the method provided by this embodiment, the network node establishesthe IP header replacement mapping according to the obtained fixed IPheader information which is bound to the UE, so, compared with anexisting manner of configuring the mapping by an MTC server or manually,the method is more flexible and can reduce difficulty in configuring andmaintaining the IP header replacement mapping; moreover, by expanding anentity for maintaining the IP header replacement mapping from an eNB inthe prior art to a network node such as a PGW or an eNB or an SGW,flexibility in obtaining the IP header replacement mapping is furtherimproved and the implementation manner becomes more universal.

Embodiment 6

This embodiment provides a network node, which is an MME or an eNB or aPGW or an SGW. Referring to FIG. 9, the network node includes:

an obtaining module 901, configured to obtain fixed IP headerinformation which is bound to a UE;

an establishing module 902, configured to establish an IP headerreplacement mapping according to the fixed IP header informationobtained by the obtaining module 901, where the IP header replacementmapping is correspondence between the fixed IP header information and anindex or a bearer; and

a communication module 903, configured to perform data transmission withthe UE according to the IP header replacement mapping established by theestablishing module 902.

When the network node is an MME or an eNB, the obtaining module 901 isconfigured to obtain, from the UE or an HSS, the fixed IP headerinformation which is bound to the UE.

When the network node is a PGW or an SGW or an eNB, the obtaining module901 is configured to receive the fixed IP header information sent by anMME after the MME obtains, from the UE or an HSS, the fixed IP headerinformation which is bound to the UE.

Further, the obtaining module 901 is configured to, when the UEinitiates an attach request or a dedicated bearer setup process, obtain,from the UE, the fixed IP header information which is bound to the UE.

Further, the obtaining module 901 is configured to receive fixed IPheader information which is bound to the UE and actively reported by theUE, or after querying the UE, receive fixed IP header information whichis bound to the UE and reported by the UE.

Specifically, when the node is an MME, the communication module 903 isconfigured to send the IP header replacement mapping to another networknode, so that the another network node performs data transmission withthe UE according to the IP header replacement mapping.

Optionally, referring to FIG. 10, when the IP header replacement mappingestablished by the establishing module 902 is correspondence between thefixed IP header information and an index, the communication module 903includes:

a first sending unit 903 a, configured to send the IP header replacementmapping established by the establishing module 902 to the UE;

a first receiving unit 903 b, configured to receive a data packet sentby the UE after the UE replaces the corresponding fixed IP headerinformation with the index in the IP header replacement mapping sent bythe first sending unit 903a; and

a first query unit 903 c, configured to query the IP header replacementmapping according to the index in the data packet which is sent by theUE and received by the first receiving unit 903 b, to obtain the fixedIP header information corresponding to the data packet sent by the UE.

Further, referring to FIG. 11, the communication module 903 furtherincludes:

a recovery unit 903 d, configured to recover the index in the datapacket sent by the UE to the corresponding fixed IP header informationobtained through query by the first query unit 903 c; and

a first forwarding unit 903 e, configured to forward, to another networknode, the data packet recovered by the recovery unit 903 d.

Optionally, referring to FIG. 12, when the IP header replacement mappingestablished by the establishing module 902 is correspondence between thefixed IP header information and an index, the communication module 903includes:

a first sending unit 903 f, configured to send the IP header replacementmapping established by the establishing module 902 to the UE; and asecond sending unit 903 g, configured to send, to the UE, a data packetwhere the corresponding fixed IP header information is replaced with theindex in the IP header replacement mapping, so that the UE queries,according to the index in the received data packet, the IP headerreplacement mapping sent by the first sending unit 903 f, to obtain thefixed IP header information corresponding to the received data packet.

Optionally, referring to FIG. 13, when the IP header replacement mappingestablished by the establishing module 902 is correspondence between thefixed IP header information and a bearer, the communication module 903includes:

an indication unit 903 h, configured to indicate, according to the IPheader replacement mapping established by the establishing module 902, abearer for the UE to send data;

a second receiving unit 903 i, configured to receive a data packet whichis sent by the UE on the bearer indicated by the indication unit 903 hand has no fixed IP header information added; and

a second query unit 903 j, configured to query the IP header replacementmapping according to the bearer for the UE to send the data packet, toobtain the fixed IP header information corresponding to the data packetwhich is sent by the UE and received by the second receiving unit 903 i.

Further, referring to FIG. 14, the communication module 903 furtherincludes:

an adding unit 903 k, configured to add, in the data packet which issent by the UE and received by the second receiving unit 903 i, thecorresponding fixed IP header information obtained through query by thesecond query unit 903 j; and

a second forwarding unit 903 l, configured to forward, to anothernetwork node, the data packet after being added with the fixed IP headerinformation by the adding unit 903 k.

The network node provided by this embodiment establishes the IP headerreplacement mapping according to the obtained fixed IP headerinformation, so, compared with an existing manner of configuring themapping by an MTC server or manually, the network node is more flexibleand can reduce difficulty in configuring and maintaining the IP headerreplacement mapping; moreover, the network node provided by thisembodiment for maintaining the IP header replacement mapping may be aneNB, and may also be an MME, or a PGW, or an SGW, so that theflexibility in obtaining the IP header replacement mapping is furtherimproved and the implementation manner becomes more universal.

It should be noted that, when the network node provided by theembodiment obtains the IP header replacement mapping, the division ofthe foregoing functional modules is taken as an example forillustration. In an actual application, the above function may beassigned, according to requirements, to different modules forimplementation, that is, the internal structure of the network node isdivided into different functional modules, so as to complete all or apart of the functions described above. Moreover, the network node andthe method for obtaining an Internet protocol header replacement mappingprovided by the foregoing embodiments belong to the same concept, andfor the specific implementation processes thereof, reference may be madeto the method embodiments, and the details are not repeated herein.

Persons of ordinary skill in the art should understand that all or apart of the steps in the method of the embodiments may be completedthrough hardware or through a program instructing related hardware. Theprogram may be stored in a computer readable storage medium including aread-only memory, a magnetic disk, an optical disk, or the like.

The above descriptions are merely preferred embodiments of the presentinvention, but are not intended to limit the present invention. Anymodification, equivalent replacement, or improvement made withoutdeparting from the spirit and principle of the present invention shallfall within the protection scope of the present invention.

What is claimed is:
 1. A method for obtaining an Internet protocolheader replacement mapping, comprising: obtaining, by a network node,fixed Internet protocol (IP) header information which is bound to a userequipment (UE), wherein the network node is a mobility management entity(MME) or an evolved base station (Enb) or a packet data network gateway(PGW) or a serving gateway (SGW); establishing an IP header replacementmapping according to the fixed IP header information, wherein the IPheader replacement mapping is correspondence between the fixed IP headerinformation and an index or a bearer; and performing data transmissionwith the UE according to the IP header replacement mapping.
 2. Themethod according to claim 1, wherein when the network node is an MME oran eNB, the obtaining the fixed Internet protocol IP header informationwhich is bound to the user equipment UE comprises: obtaining, from theUE or a home subscriber server (HSS), the fixed IP header informationwhich is bound to the UE; or, when the network node is a PGW or an SGWor an eNB, the obtaining the fixed Internet protocol IP headerinformation which is bound to the user equipment UE comprises: receivingthe fixed IP header information sent by an MME after the MME obtains,from the UE or a home subscriber server HSS, the fixed IP headerinformation which is bound to the UE.
 3. The method according to claim2, wherein the obtaining, from the UE, the fixed IP header informationwhich is bound to the UE comprises: when the UE initiates an attachrequest or a dedicated bearer setup process, obtaining, from the UE, thefixed IP header information which is bound to the UE.
 4. The methodaccording to claim 2, wherein the obtaining, from the UE, the fixed IPheader information which is bound to the UE comprises: receiving fixedIP header information which is bound to the UE and actively reported bythe UE, or after querying the UE, receiving fixed IP header informationwhich is bound to the UE and reported by the UE.
 5. The method accordingto claim 1, wherein when the network node is an MME, the performing datatransmission with the UE according to the IP header replacement mappingcomprises: sending the IP header replacement mapping to another networknode, so that the another network node performs data transmission withthe UE according to the IP header replacement mapping.
 6. The methodaccording to claim 1, wherein when the IP header replacement mapping iscorrespondence between the fixed IP header information and an index, theperforming data transmission with the UE according to the IP headerreplacement mapping comprises: sending the IP header replacement mappingto the UE, and receiving a data packet sent by the UE after the UEreplaces the corresponding fixed IP header information with the index inthe IP header replacement mapping; and querying the IP headerreplacement mapping according to the index in the data packet sent bythe UE, to obtain the fixed IP header information corresponding to thedata packet sent by the UE.
 7. The method according to claim 6, whereinafter the obtaining the fixed IP header information corresponding to thedata packet sent by the UE, the method further comprises: recovering theindex in the data packet sent by the UE to the corresponding fixed IPheader information, and forwarding the fixed IP header information toanother network node.
 8. The method according to claim 1, wherein whenthe IP header replacement mapping is correspondence between the fixed IPheader information and an index, the performing data transmission withthe UE according to the IP header replacement mapping comprises: sendingthe IP header replacement mapping to the UE, and sending, to the UE, adata packet where the corresponding fixed IP header information isreplaced with the index in the IP header replacement mapping, so thatthe UE queries the IP header replacement mapping according to the indexin the received data packet, to obtain the fixed IP header informationcorresponding to the received data packet.
 9. The method according toclaim 1, wherein when the IP header replacement mapping iscorrespondence between the fixed IP header information and a bearer, theperforming data transmission with the UE according to the IP headerreplacement mapping comprises: indicating, according to the IP headerreplacement mapping, a bearer for the UE to send data, and receiving adata packet which is sent by the UE on the indicated bearer and has nofixed IP header information added; and querying the IP headerreplacement mapping according to the bearer for the UE to send the datapacket, to obtain the fixed IP header information corresponding to thedata packet sent by the UE.
 10. The method according to claim 9, whereinafter the obtaining the fixed IP header information corresponding to thedata packet sent by the UE, the method further comprises: adding thecorresponding fixed IP header information in the data packet sent by theUE, and forwarding the data packet to another network node.
 11. Anetwork node, wherein the network node is a mobility management entity(MME) or an evolved base station (eNB) or a packet data network gateway(PGW) or a serving gateway (SGW), and comprises: an obtaining module,configured to obtain fixed Internet protocol (IP) header informationwhich is bound to a user equipment (UE); an establishing module,configured to establish an IP header replacement mapping according tothe fixed IP header information obtained by the obtaining module,wherein the IP header replacement mapping is correspondence between thefixed IP header information and an index or a bearer; and acommunication module, configured to perform data transmission with theUE according to the IP header replacement mapping established by theestablishing module.
 12. The node according to claim 11, wherein whenthe network node is an MME or an eNB, the obtaining module is configuredto obtain, from the UE or a home subscriber server HSS, fixed IP headerinformation which is bound to the UE; or, when the network node is a PGWor an SGW or an eNB, the obtaining module is configured to receive thefixed IP header information sent by an MME after the MME obtains, fromthe UE or a home subscriber server (HSS), the fixed IP headerinformation which is bound to the UE.
 13. The node according to claim12, wherein the obtaining module is configured to, when the UE initiatesan attach request or a dedicated bearer setup process, obtain, from theUE, the fixed IP header information which is bound to the UE.
 14. Thenode according to claim 12, wherein the obtaining module is configuredto receive fixed IP header information which is bound to the UE andactively reported by the UE, or after querying the UE, receive fixed IPheader information which is bound to the UE and reported by the UE. 15.The node according to claim 11, wherein when the node is an MME, thecommunication module is configured to send the IP header replacementmapping to another network node, so that the another network nodeperforms data transmission with the UE according to the IP headerreplacement mapping.
 16. The node according to claim 11, wherein whenthe IP header replacement mapping established by the establishing moduleis correspondence between the fixed IP header information and an index,the communication module comprises: a first sending unit, configured tosend the IP header replacement mapping established by the establishingmodule to the UE; a first receiving unit, configured to receive a datapacket sent by the UE after the UE replaces the corresponding fixed IPheader information with the index in the IP header replacement mappingsent by the first sending unit; and a first query unit, configured toquery the IP header replacement mapping according to the index in thedata packet which is sent by the UE and received by the first receivingunit, to obtain the fixed IP header information corresponding to thedata packet sent by the UE.
 17. The node according to claim 16, whereinthe communication module further comprises: a recovery unit, configuredto recover the index in the data packet sent by the UE to thecorresponding fixed IP header information obtained through query by thefirst query unit; and a first forwarding unit, configured to forward, toanother network node, the data packet recovered by the recovery unit.18. The node according to claim 11, wherein when the IP headerreplacement mapping established by the establishing module iscorrespondence between the fixed IP header information and an index, thecommunication module comprises: a first sending unit, configured to sendthe IP header replacement mapping established by the establishing moduleto the UE; and a second sending unit, configured to send, to the UE, adata packet where the corresponding fixed IP header information isreplaced with the index in the IP header replacement mapping, so thatthe UE queries, according to the index in the received data packet, theIP header replacement mapping sent by the first sending unit, to obtainthe fixed IP header information corresponding to the received datapacket.
 19. The node according to claim 11, wherein when the IP headerreplacement mapping established by the establishing module iscorrespondence between the fixed IP header information and a bearer, thecommunication module comprises: an indication unit, configured toindicate, according to the IP header replacement mapping established bythe establishing module, a bearer for the UE to send data; a secondreceiving unit, configured to receive a data packet which is sent by theUE on the bearer indicated by the indication unit and has no fixed IPheader information added; and a second query unit, configured to querythe IP header replacement mapping according to the bearer for the UE tosend the data packet, to obtain the fixed IP header informationcorresponding to the data packet which is sent by the UE and received bythe second receiving unit.
 20. The node according to claim 19, whereinthe communication module further comprises: an adding unit, configuredto add, in the data packet which is sent by the UE and received by thesecond receiving unit, the corresponding fixed IP header informationobtained through query by the second query unit; and a second forwardingunit, configured to forward, to another network node, the data packetafter being added with the fixed IP header information by the addingunit.